From course document
Group Number 6
EARS Project Assigned
We are just using a document based Waterfall methodology
| Document Name | Deadline | Weight |
|---|---|---|
| D1 Project Plan do not hand in | Optional Feb 2 |
0% |
| D2 Requirements and specification | Feb 9 | 15% |
| D3 Architecture and User Interface Design | Feb 23 | 5% |
| D4 Detailed Design | Mar 13 | 25% |
| D5 Implementation | Mar 29 | 40% |
| D6 Testing | Apr 5 | 5% |
| Progress Presentation recorded | Apr 5 | 10% |
Projects wil be implemented using C++/Java for Windows
Yikes, I use Linux so maybe I shouldn't do coding
There will be one project progress presentation and one final demonstration.
The progress presentation will be hold in XXX,
which worth of your project.
Towards the last week (probably during the last week, but possibly earlier),
each team will demonstrate the program they have developed to the "client(s)".
These should be geared towards "selling" the product.
These presentations not only are assessed,
but also the products on which they are based will be assessed
Project 4 Employment Application Review System
EARS is an intranet-based Employment Application Review System for the Department of Math and Computer Science in Algoma University.
The system is designed so that department faculty members can review applicants and collaborate asynchronously in order to find the best applicant for a given job opening.
This system reduces the overhead of the process and lightens the workload for the search chairperson.
The scope of this project will be to provide a system that allows the CCMT to:
Review following links (in no specific order) for writing an effective SRS
Wikipedia ~ Software Requirements Specifications
Circle - Visual Paradigms ~ UML and Requirement Diagram
exinfm.com - Training ~ SRS Template
Your 2023 Guide to Writing a Software Requirements Specification – SRS Document by Andrew Burak CEO at Relevant
Blog Article
How to Write a Software Requirements Specification (SRS Document)
by Gerhard Krüger and Charles Lane
Blog Article
How to Create Requirements Spec. in Minutes?
Visual Paradigms ~ How to Create Software Requirements Spec with Doc Composer
Requirement Diagrams
Visual Paradigms
From Wikipedia ~ Software Requirements Specifications
It may include use cases
Following the idea of code smells, the notion of requirements smell has been proposed to describe issues in requirements specification where the requirement is not necessarily wrong but could be problematic
Examples of requirements smells are
Lucas ~ Project Demo/Presentation
UML ~
Coding ~ Java
Prepared by Lucas Cekan
Product: Employment Application Review System
This is a software requirements specification (SRS) document whose purpose is to define the requirements, purpose, limitation, features both functional and non-functional of this software product.
This document is prepared for a technical and non-technical audience alike for the purpose of laying out the features and requirements to start developing this software project.
This SRS is for the development of a Employment Application Review System (EARS)
The intended users of this system are the department faculty members at Algoma University at the Department of Math and Computer Science.
The software is meant to make the process of reviewing applications much easier and quicker. The costs in terms of overhead of effort, time and attention of reviewers should be reduced.
The goal of the system is to allow
This document will list the requirements and the features of this system. The features will divided into sub parts for example the login process and the faculty search listing the requirements for each sub-part.
This document will list a couple of intended use cases that should demonstrate how the software is intended to be used if the requirements are met.
The document will list the functional requirement, that is the basic requirements that must be met for this product to function and non-functional requirements, or the requirements that will add to the user experience but are not necessarily required for the product to function.
Software limitations will be listed based on the skills and experience of the developers assigned to this project. The use of Java and development software from the Java ecosystem such as JavaFX will be discussed.
Here is a detailed description of the product and it's features
The system will be based on the following categories
Users of this system must be able to
Each applications should be represented in the system by a profile, with comments from reviewers and a status representing
The profile should display the
The system should allow users to search the department's faculty members. Which should find the members and display their position starting and ending dates.
The current Committee chair should be displayed predominately and should be quickly found.
The various views and the interfaces that a user would be confronted by are described here.
Users need to be able to login through a login screen when at the start of the applications.
Users should be able to go back to this view once if they choose to log off.
Users log in with their credentials that being their email and password.
After the login process the users should be confronted with the main interface divided into sections.
A list of applications awaiting review
The header with information and icons for who is logged in and a attention icon that indicate that the user was assigned applications for review. The current committee chair should be displayed prominently.
A search bar for a faculty search, to find a faculty member quickly with a dropdown quickly displaying a starting date, ending date, position and a icon to add the member to the committee.
For each application there should be a profile displaying the applicant's typed application and list of their skills, proficiencies, education and so on. Followed by a comment thread below that users can discuss with each other about the application.
There should be action icons so that user can request a faculty review. The system should then record that this application has already been reviewed by the user.